Hey guys searching searching searching but didnt found the asnwer. The problem we have alot of users and since 2 months we have 40 pc running windows 7. Most of them work perfect (after alot of coding) but we run into some problems. Some pc`s dont run the computer startupscript, we made a policy to run the computer script but on some computers it doenst work. All the pc are the same, have the same security groups. We have another policy "Always wait for the network at computer startup and logon" and we have the policy " Run startup scripts synchronously" So again everything works on most computers but some just don`t wait for the network, they skip the policy because the network isn`t ready yet? Whats happening here? Update: ok so i figured out that if i add a reg setting (or policy) that it works but i have to wait for 60 sec before the network/pc is ready, were all on the same network some people have no problems some do. regsetting: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon "GpNetworkStartTimeoutPolicyValue"=dword:00000019 regsetting: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters "DisableDHCPMediaSense"=dword:00000001 Its 60seconds right nog if i put it to 24 sec the startup computerscript isnt triggered! at 60 seconds it works! So its odd that some pc have no problem and some have to wait for 60 seconds before everything works..... Is there a retry option in AD before it tries to push the policy again after it failed the first time?

As I know there is no such setting. Because the computer cannot adjust if the script is run properly. You may consider add the tasks via Task Scheduler.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

If i use the two reg settings: regsetting: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon "GpNetworkStartTimeoutPolicyValue"=dword:00000019 regsetting: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters "DisableDHCPMediaSense"=dword:00000001 Everything works so the network is ready when the computerscript starts but the users have to wait 60 seconds before the network is ready. If we disable the regsetting no computerscript and no logonscript (user) We all have 1gb network lan, iam guessing this is the problem but i cant find a solution anywhere...... Are we the only one having this problem?

If i use the two reg settings: regsetting: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon "GpNetworkStartTimeoutPolicyValue"=dword:00000019 regsetting: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters "DisableDHCPMediaSense"=dword:00000001 Everything works so the network is ready when the computerscript starts but the users have to wait 60 seconds before the network is ready. If we disable the regsetting no computerscript and no logonscript (user) We all have 1gb network lan, iam guessing this is the problem but i cant find a solution anywhere...... Are we the only one having this problem? I know its kind of an old thread, but no, you are not the only one having this problem. I'm using the "Wait for Network Connection" policy, and without those registry keys you provided, none of the Computer Policies are applied. Real quick I see Preparing Network Connections, but then it goes to the "Press Ctrl + Alt + Delete" and I had to first log onto a local account, because it wasn't connected to a domain. Then after that I could login as a Domain User (or in my case a Domain Admin). I even tried doing multiple gpupdate commands. I tried gpupdate gpupdate /force gpupdate /force /boot gpupdate /force /boot /Sync << This must be run as an Admin And those didn't even do anything from what it seemed like. Although it was showing the message we have set after the Ctrl + Alt + Delete which meant we was getting closer. Now after the Registry Tweaks you provided, when the computer starts, it finally applies the policies and you can see "Applying Computer Settings" which wasn't there before. Thanks :)

Glad it helped you, it solves a lot of problems BUT i think its wrong from MS thats it needs this as a fix... We also changed our switches (spanning tree fast protocol) which also helps alot :)